Skip to content

Changelog: September 25, 2026 - #80

Open
zeyu2001 wants to merge 1 commit into
mainfrom
changelog/5be31f4a0
Open

zeyu2001 wants to merge 1 commit into
mainfrom
changelog/5be31f4a0

Conversation

@zeyu2001

@zeyu2001 zeyu2001 commented Sep 25, 2026 •

Copy link
Copy Markdown
Member
  • Date: September 25, 2026
  • Commit: 5be31f4a0

Documentation TODOs

These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:

  • Browser authentication for Whitebox scans: New docs page needed explaining how to supply login credentials (username/password or session token) in the Whitebox scan wizard, what the preview flow looks like, and which authentication methods are supported.
  • Manual finding retests: New docs page needed covering how to request a retest from the finding detail, what the retest workflow looks like from the customer's perspective, and what outcomes are possible.
  • GitHub repository selection in-app: Update /platform/repositories/github (or add a section) to explain in-app enable/disable of individual GitHub repositories and the auto-reselect behavior for restored repos.
  • Review replies on explicit @HacktronAI review requests: Update Code Review docs to note that explicit review requests now receive a reply even when the commit was already scanned.
  • Large estimate gating (5,000+ credits): Document the threshold in Whitebox billing/cost-estimation docs and what the customer should expect (contact prompt rather than a total).

Note

Low Risk
Documentation-only changelog update with no application or infrastructure code changes.

Overview
Adds the September 25, 2026 changelog release notes and bumps the CHANGELOG:INSERT last-prod-sha to 5be31f4a0.

The new entry documents shipped platform changes: Whitebox scan browser login credentials in the wizard, manual finding retests from finding detail, in-app GitHub repo enable/disable (with auto-reselect), a Repositories table refresh (Owner column, scoped filters, Open Findings / Last Scan), People server-side search/filter/sort/pagination fixes, @HacktronAI review replies when a commit was already scanned, 5,000+ credit Whitebox estimates prompting contact instead of a total, and GitHub PR review on self-hosted appliances. Links point at existing docs paths; the PR description lists follow-up doc work for several items.

Reviewed by Cursor Bugbot for commit 784d28e. Bugbot is set up for automated code reviews on this repo. Configure here.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-25T09:11:14.021925Z 784d28e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 784d28ea84

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread changelog.mdx

**Review replies on explicit requests**: When you request a review from @hacktronai on a pull or merge request that Hacktron already scanned at that commit, you now receive a direct reply with the existing result. Previously the request went unanswered on a cached scan.

**Large scan estimates routed to the team**: Whitebox cost estimates above 5,000 credits no longer show a total in the wizard. Instead, you are prompted to contact the team directly so pricing can be confirmed before the scan starts.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Describe the 5,000-credit boundary accurately

The commit's own documentation TODO defines this gate as applying to estimates of 5,000 credits or more, but “above 5,000” excludes an estimate of exactly 5,000. At that boundary, customers are therefore told to expect a total when the wizard instead prompts them to contact the team; use “5,000 credits or more” to match the shipped threshold.

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants